Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 87a7167e09e4260df8245fd1a662264d415bf401460f47fff036d552978fdf7d

Tx prefix hash: d470b73a1ef0ec4e27527bc09e0c6940af6963b37a22b1c0c1523c668b1dd656
Tx public key: aa1f1293fb449798beef11e3c7257dfe746b86c8582a5de58c60bf8f94f97874
Timestamp: 1714993369 Timestamp [UCT]: 2024-05-06 11:02:49 Age [y:d:h:m:s]: 00:338:09:24:39
Block: 1016045 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 241884 RingCT/type: yes/0
Extra: 01aa1f1293fb449798beef11e3c7257dfe746b86c8582a5de58c60bf8f94f9787402110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f6666502dc54845d5126da4498952f31d29cbfe45c2f68c8bc7cf8888fda5153 0.600000000000 1479520 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": 1016055, "vin": [ { "gen": { "height": 1016045 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f6666502dc54845d5126da4498952f31d29cbfe45c2f68c8bc7cf8888fda5153" } } ], "extra": [ 1, 170, 31, 18, 147, 251, 68, 151, 152, 190, 239, 17, 227, 199, 37, 125, 254, 116, 107, 134, 200, 88, 42, 93, 229, 140, 96, 191, 143, 148, 249, 120, 116, 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