Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab7b7fc35f83a615535c81689227b09ed8d3dd6971d0a254a456a0ad1e67658d

Tx prefix hash: a19574b34a7fdbce92cbc30dd026a3f18b55978d27c38817405b67f3d1b8876c
Tx public key: e1e8e4b3422590c9f9a551f28a48f53bf90c8d820c2041abb3546e7df467f351
Timestamp: 1717846290 Timestamp [UCT]: 2024-06-08 11:31:30 Age [y:d:h:m:s]: 00:294:01:51:12
Block: 1039697 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 210156 RingCT/type: yes/0
Extra: 01e1e8e4b3422590c9f9a551f28a48f53bf90c8d820c2041abb3546e7df467f3510211000000060011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3318f3dccdb179e5c9d32dd29870438880065fc572cb015e1d0a7426b502c946 0.600000000000 1508350 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": 1039707, "vin": [ { "gen": { "height": 1039697 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3318f3dccdb179e5c9d32dd29870438880065fc572cb015e1d0a7426b502c946" } } ], "extra": [ 1, 225, 232, 228, 179, 66, 37, 144, 201, 249, 165, 81, 242, 138, 72, 245, 59, 249, 12, 141, 130, 12, 32, 65, 171, 179, 84, 110, 125, 244, 103, 243, 81, 2, 17, 0, 0, 0, 6, 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