Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f56d07fb6294b689be8a80f6ba7bcd6f3080955bcab088ed64f088622e607036

Tx prefix hash: 5e0679fe10f1ac21fd08f2ce7417999f151c0e65eb0cfa8a3ce9f7d5134fa4ad
Tx public key: 5902e867fb1f4b0b60750b42be6260f219a3f6878bcea253cc0caaedafea5224
Timestamp: 1720296832 Timestamp [UCT]: 2024-07-06 20:13:52 Age [y:d:h:m:s]: 00:344:06:33:04
Block: 1060013 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 245945 RingCT/type: yes/0
Extra: 015902e867fb1f4b0b60750b42be6260f219a3f6878bcea253cc0caaedafea522402110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c2cef4916c9752269d8f037f5326903d5707a0405578b4fcb1f0e824f5da5764 0.600000000000 1530484 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": 1060023, "vin": [ { "gen": { "height": 1060013 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c2cef4916c9752269d8f037f5326903d5707a0405578b4fcb1f0e824f5da5764" } } ], "extra": [ 1, 89, 2, 232, 103, 251, 31, 75, 11, 96, 117, 11, 66, 190, 98, 96, 242, 25, 163, 246, 135, 139, 206, 162, 83, 204, 12, 170, 237, 175, 234, 82, 36, 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