Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 515c2cda6592df3ece3d70f114d738e7d3989aa5505cf96ae9c5680934650ac3

Tx prefix hash: 1f5776e0acd3967241d798e2a896ee4f7cb1cb38f57a25ad5b9d7794856068fc
Tx public key: fc64e38471f7d7f70970b590469e44cc7aee857206aa324d1d8cfc5921e6416e
Timestamp: 1703076351 Timestamp [UCT]: 2023-12-20 12:45:51 Age [y:d:h:m:s]: 01:169:19:38:44
Block: 917253 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 382537 RingCT/type: yes/0
Extra: 01fc64e38471f7d7f70970b590469e44cc7aee857206aa324d1d8cfc5921e6416e0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e54d8ce65e572b73cd43f58e6bbffc1334526b7bda0068e535c28f6d6dd6d0d6 0.600000000000 1374823 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": 917263, "vin": [ { "gen": { "height": 917253 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e54d8ce65e572b73cd43f58e6bbffc1334526b7bda0068e535c28f6d6dd6d0d6" } } ], "extra": [ 1, 252, 100, 227, 132, 113, 247, 215, 247, 9, 112, 181, 144, 70, 158, 68, 204, 122, 238, 133, 114, 6, 170, 50, 77, 29, 140, 252, 89, 33, 230, 65, 110, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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