Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60275225a53f0c9e52af32f406072f74fd9d4eb98dbb95c8f6b1554393fc3b3c

Tx prefix hash: 9434e080ebcfdde8bd9cc9fb4a8087d3a3e60acdcbff8387b3c6f6a2935a0374
Tx public key: 84b5390c760a8e78762ad6f42ac520b0d0b44e32fe46d7a934872da169f9ee35
Timestamp: 1703203545 Timestamp [UCT]: 2023-12-22 00:05:45 Age [y:d:h:m:s]: 01:066:21:03:45
Block: 918304 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 308898 RingCT/type: yes/0
Extra: 0184b5390c760a8e78762ad6f42ac520b0d0b44e32fe46d7a934872da169f9ee3502110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8a1435da954deb92be124e832e754f8ae3861c0e76615e74abac325a6eb74be2 0.600000000000 1375946 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": 918314, "vin": [ { "gen": { "height": 918304 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8a1435da954deb92be124e832e754f8ae3861c0e76615e74abac325a6eb74be2" } } ], "extra": [ 1, 132, 181, 57, 12, 118, 10, 142, 120, 118, 42, 214, 244, 42, 197, 32, 176, 208, 180, 78, 50, 254, 70, 215, 169, 52, 135, 45, 161, 105, 249, 238, 53, 2, 17, 0, 0, 0, 2, 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