Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8740d05f70b5afcbf84c306085e6fa49ad22182018a6d5bca78f713e812e9bc9

Tx prefix hash: 95b4e0e731515cb66a64a7e033eacc2e6651b0ff9103a1cc7808414a5ab189d1
Tx public key: 8ddfdfe32ba3f625062d5c4e21f1aa8d2de88d98cb700216518591569ca6feb4
Timestamp: 1725946999 Timestamp [UCT]: 2024-09-10 05:43:19 Age [y:d:h:m:s]: 00:165:23:28:55
Block: 1106866 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 118410 RingCT/type: yes/0
Extra: 018ddfdfe32ba3f625062d5c4e21f1aa8d2de88d98cb700216518591569ca6feb4021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 990965516bb7d7d529e21d7db3d785153f762c80083f9391ac482e618839bee4 0.600000000000 1584467 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": 1106876, "vin": [ { "gen": { "height": 1106866 } } ], "vout": [ { "amount": 600000000, "target": { "key": "990965516bb7d7d529e21d7db3d785153f762c80083f9391ac482e618839bee4" } } ], "extra": [ 1, 141, 223, 223, 227, 43, 163, 246, 37, 6, 45, 92, 78, 33, 241, 170, 141, 45, 232, 141, 152, 203, 112, 2, 22, 81, 133, 145, 86, 156, 166, 254, 180, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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