Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b67dfa3949772d1af4f7ec8919d0aca1a90cd57dc980dca752f28f173598dc1

Tx prefix hash: ee86a4455d01ed53576f67c722f9e0d5ddd696431a784286d4ac723afaeb59d6
Tx public key: 30ac62208356ba41b39a8bbcbcf6a3be4210dd9af40c7c0cb6bd57e222cae2cc
Timestamp: 1710044656 Timestamp [UCT]: 2024-03-10 04:24:16 Age [y:d:h:m:s]: 01:245:16:51:50
Block: 975031 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 434311 RingCT/type: yes/0
Extra: 0130ac62208356ba41b39a8bbcbcf6a3be4210dd9af40c7c0cb6bd57e222cae2cc0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fa8d7dd80e2928f38e89f47686fd64f19b2d5f0ac30e4ba9c52d218c2d642e75 0.600000000000 1435002 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": 975041, "vin": [ { "gen": { "height": 975031 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fa8d7dd80e2928f38e89f47686fd64f19b2d5f0ac30e4ba9c52d218c2d642e75" } } ], "extra": [ 1, 48, 172, 98, 32, 131, 86, 186, 65, 179, 154, 139, 188, 188, 246, 163, 190, 66, 16, 221, 154, 244, 12, 124, 12, 182, 189, 87, 226, 34, 202, 226, 204, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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