Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f02df4852cd67ff95592b778c834b7e4809caa504699e417bf440632601317e4

Tx prefix hash: 7511cdd2a3345f57162a920541785391c61bbc723aefbb5006af15535af4a6cf
Tx public key: ef3d4a330dccacc5b5d93cea4d1d249d679931f1be4870a6470f2c3cd7bc96b0
Timestamp: 1712852930 Timestamp [UCT]: 2024-04-11 16:28:50 Age [y:d:h:m:s]: 01:042:13:56:37
Block: 998280 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 291444 RingCT/type: yes/0
Extra: 01ef3d4a330dccacc5b5d93cea4d1d249d679931f1be4870a6470f2c3cd7bc96b00211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a66d6ff9d2f5dc3d48fdfc8b8604fdde36ec822b32bfe3c0cd6c5a08a92eb77 0.600000000000 1458726 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": 998290, "vin": [ { "gen": { "height": 998280 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a66d6ff9d2f5dc3d48fdfc8b8604fdde36ec822b32bfe3c0cd6c5a08a92eb77" } } ], "extra": [ 1, 239, 61, 74, 51, 13, 204, 172, 197, 181, 217, 60, 234, 77, 29, 36, 157, 103, 153, 49, 241, 190, 72, 112, 166, 71, 15, 44, 60, 215, 188, 150, 176, 2, 17, 0, 0, 0, 3, 122, 156, 244, 199, 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