Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e244a5c1940d1214c7c29fc5d2ddb8a0b79578304c3750ceceed601652f16b94

Tx prefix hash: 9c3d4f020ec8b4f9550eddddd9a017733a3e73b219d292d2add047d01a9c984e
Tx public key: e2847d39159780c6da84cdcc4e6cd77cd9629e321269aae403d14d9c4e14f15b
Timestamp: 1730035592 Timestamp [UCT]: 2024-10-27 13:26:32 Age [y:d:h:m:s]: 00:073:19:13:35
Block: 1140712 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 52766 RingCT/type: yes/0
Extra: 01e2847d39159780c6da84cdcc4e6cd77cd9629e321269aae403d14d9c4e14f15b021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fcfe4f6bc072f8d8c371f19820d423219c4d15bebd19cf745bb1bf01220ffe99 0.600000000000 1624515 of 15

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": 1140722, "vin": [ { "gen": { "height": 1140712 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fcfe4f6bc072f8d8c371f19820d423219c4d15bebd19cf745bb1bf01220ffe99" } } ], "extra": [ 1, 226, 132, 125, 57, 21, 151, 128, 198, 218, 132, 205, 204, 78, 108, 215, 124, 217, 98, 158, 50, 18, 105, 170, 228, 3, 209, 77, 156, 78, 20, 241, 91, 2, 17, 0, 0, 0, 8, 0, 127, 151, 138, 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