Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd1023f8df6b817ad1548c670128d4aa16a480bc55e7f6e029885465e4aa9d3d

Tx prefix hash: 781f6246cb73859a248b188ff63b56b0e4e9b76e345351d0ca6a23e2ff91893f
Tx public key: 8b24060b1e5086da6ec2074fd1316c1cbc4d21b4cd03c67e923948cb40b8c729
Timestamp: 1720066309 Timestamp [UCT]: 2024-07-04 04:11:49 Age [y:d:h:m:s]: 00:315:19:16:32
Block: 1058100 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 225669 RingCT/type: yes/0
Extra: 018b24060b1e5086da6ec2074fd1316c1cbc4d21b4cd03c67e923948cb40b8c72902110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0be0613b368c9a681b1fdbe8e3abf20fd261e8ecc5008c3472f7c627a45d9a1 0.600000000000 1528549 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": 1058110, "vin": [ { "gen": { "height": 1058100 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0be0613b368c9a681b1fdbe8e3abf20fd261e8ecc5008c3472f7c627a45d9a1" } } ], "extra": [ 1, 139, 36, 6, 11, 30, 80, 134, 218, 110, 194, 7, 79, 209, 49, 108, 28, 188, 77, 33, 180, 205, 3, 198, 126, 146, 57, 72, 203, 64, 184, 199, 41, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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