Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: df3cac725c387571ae52143da2bcd6fdc5cfd373f71b84c9201a2de8c836a81c

Tx prefix hash: 2d8b15fa363c50ddfd9b3f1bfeb0768400ace662cba126318215f3a8e3eacd29
Tx public key: 504d86a2d2d0e411c262a8e59bb164f47e8cecf8591c96240aaa369029d189b5
Timestamp: 1677788845 Timestamp [UCT]: 2023-03-02 20:27:25 Age [y:d:h:m:s]: 01:275:11:15:43
Block: 708488 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 457789 RingCT/type: yes/0
Extra: 01504d86a2d2d0e411c262a8e59bb164f47e8cecf8591c96240aaa369029d189b502110000000133af99f4000000000000000000

1 output(s) for total of 2.757306531000 dcy

stealth address amount amount idx
00: 6c7cc457357d09e4f1b25537b75408792c6bd41bcf405d324e187dcc532b3531 2.757306531000 1152385 of 0

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 708498, "vin": [ { "gen": { "height": 708488 } } ], "vout": [ { "amount": 2757306531, "target": { "key": "6c7cc457357d09e4f1b25537b75408792c6bd41bcf405d324e187dcc532b3531" } } ], "extra": [ 1, 80, 77, 134, 162, 210, 208, 228, 17, 194, 98, 168, 229, 155, 177, 100, 244, 126, 140, 236, 248, 89, 28, 150, 36, 10, 170, 54, 144, 41, 209, 137, 181, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8