Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89fbfb796ea3a534dffec783faaaef71149004f62ca4ec7a3045c56763ae3b69

Tx prefix hash: 223037d8dc121a6ea1ce261f856b36bc75d8a57a19b409de710ac2d22b0e19ed
Tx public key: 17f1b1a70d89cd977b53a30b56e186d146566e60d22bbae9d2d45d66ab8c9d31
Timestamp: 1734660600 Timestamp [UCT]: 2024-12-20 02:10:00 Age [y:d:h:m:s]: 00:104:23:54:34
Block: 1179006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74799 RingCT/type: yes/0
Extra: 0117f1b1a70d89cd977b53a30b56e186d146566e60d22bbae9d2d45d66ab8c9d31021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e95276e996b607850a3784b5b22cbf5762bf2abe1672d8ddb0dd330271885ad7 0.600000000000 1665397 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": 1179016, "vin": [ { "gen": { "height": 1179006 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e95276e996b607850a3784b5b22cbf5762bf2abe1672d8ddb0dd330271885ad7" } } ], "extra": [ 1, 23, 241, 177, 167, 13, 137, 205, 151, 123, 83, 163, 11, 86, 225, 134, 209, 70, 86, 110, 96, 210, 43, 186, 233, 210, 212, 93, 102, 171, 140, 157, 49, 2, 17, 0, 0, 0, 2, 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