Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 51e9d877dff464ceb2100d14b1d1060cb1ed1838a9de6661d4e496a97aef1f01

Tx prefix hash: 118c7ec714fe554bd366a4c378390edffe0ddd415666b1b326a99fb4894982e7
Tx public key: dcb9ef6899ebb1c30f4f0e8141d1016ce847f74fdc88cca7af67c73e71b41ed7
Timestamp: 1711634617 Timestamp [UCT]: 2024-03-28 14:03:37 Age [y:d:h:m:s]: 01:027:19:37:58
Block: 988219 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 280847 RingCT/type: yes/0
Extra: 01dcb9ef6899ebb1c30f4f0e8141d1016ce847f74fdc88cca7af67c73e71b41ed702110000000459dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e85f5eaa1c584fb599199ed1131d45eb9de51bee04cb61b28652364f728214ea 0.600000000000 1448490 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": 988229, "vin": [ { "gen": { "height": 988219 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e85f5eaa1c584fb599199ed1131d45eb9de51bee04cb61b28652364f728214ea" } } ], "extra": [ 1, 220, 185, 239, 104, 153, 235, 177, 195, 15, 79, 14, 129, 65, 209, 1, 108, 232, 71, 247, 79, 220, 136, 204, 167, 175, 103, 199, 62, 113, 180, 30, 215, 2, 17, 0, 0, 0, 4, 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