Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9411c23d7e82cb2b5c1d7b05c6856608e8efa199add9bda9847f6124a90ef13d

Tx prefix hash: 671cbcfeb9412c9219529bbcaed76259df69fd2cfee97b13712cdd1bfc405bec
Tx public key: 22227eaabf1f0eedaf4d33d319ee4653e56ffda073dc4f6b867325d7f1016474
Timestamp: 1718617187 Timestamp [UCT]: 2024-06-17 09:39:47 Age [y:d:h:m:s]: 00:294:09:03:17
Block: 1046090 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210353 RingCT/type: yes/0
Extra: 0122227eaabf1f0eedaf4d33d319ee4653e56ffda073dc4f6b867325d7f101647402110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e766249d8601b02886c7a83b40aee2c603d0fc250674b0cd73f4678a1e8f8b8c 0.600000000000 1515849 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": 1046100, "vin": [ { "gen": { "height": 1046090 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e766249d8601b02886c7a83b40aee2c603d0fc250674b0cd73f4678a1e8f8b8c" } } ], "extra": [ 1, 34, 34, 126, 170, 191, 31, 14, 237, 175, 77, 51, 211, 25, 238, 70, 83, 229, 111, 253, 160, 115, 220, 79, 107, 134, 115, 37, 215, 241, 1, 100, 116, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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