Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fffb8419e05e9815dc6a396e1e2194cdc8708a2e0ac4b3b4c1fac7c0fc4b772a

Tx prefix hash: 661b1d17a94c1ca49d9bf74ea3b93caccd6cf82f722a7df4de25a94e3184d3c5
Tx public key: 9674a5c1f9f6896da87a719a65fef2ec3c28c994119701491e59d6c45a237a34
Timestamp: 1727402218 Timestamp [UCT]: 2024-09-27 01:56:58 Age [y:d:h:m:s]: 00:186:16:25:46
Block: 1118922 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133222 RingCT/type: yes/0
Extra: 019674a5c1f9f6896da87a719a65fef2ec3c28c994119701491e59d6c45a237a3402110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6b0e2b982913dcedc7e9518bd082e903858338c69297e70f8f7dc11f4680e6f0 0.600000000000 1600283 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": 1118932, "vin": [ { "gen": { "height": 1118922 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6b0e2b982913dcedc7e9518bd082e903858338c69297e70f8f7dc11f4680e6f0" } } ], "extra": [ 1, 150, 116, 165, 193, 249, 246, 137, 109, 168, 122, 113, 154, 101, 254, 242, 236, 60, 40, 201, 148, 17, 151, 1, 73, 30, 89, 214, 196, 90, 35, 122, 52, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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