Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0dcd4bc0550497afa8966e92291791bab1a0f8e6f89d83c55d83bc8c351eabb0

Tx prefix hash: fca119cccc104ed761038fd8e694dbd82035c13412ab07214778c29b82a64b72
Tx public key: b144ecb5e508d2f4cbe6928157787d314d1f3e6f759b2d59ceb15dc0018d6361
Timestamp: 1719724483 Timestamp [UCT]: 2024-06-30 05:14:43 Age [y:d:h:m:s]: 00:308:00:30:22
Block: 1055264 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 220110 RingCT/type: yes/0
Extra: 01b144ecb5e508d2f4cbe6928157787d314d1f3e6f759b2d59ceb15dc0018d636102110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c3f7fca442dbfa2f997ad1675bb518ae6d77afe7686d7c3b1074d5405eb44d3 0.600000000000 1525661 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": 1055274, "vin": [ { "gen": { "height": 1055264 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c3f7fca442dbfa2f997ad1675bb518ae6d77afe7686d7c3b1074d5405eb44d3" } } ], "extra": [ 1, 177, 68, 236, 181, 229, 8, 210, 244, 203, 230, 146, 129, 87, 120, 125, 49, 77, 31, 62, 111, 117, 155, 45, 89, 206, 177, 93, 192, 1, 141, 99, 97, 2, 17, 0, 0, 0, 5, 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