Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 376e7c9ec01dd248e9cb1cc9306618635b4692a07d8b66188c0ec372b9460986

Tx prefix hash: f8f509b9d619d8446895ab04bf40a2716bdb11d89d1d62f02e700a15b7012a56
Tx public key: c3ee2d19dd1561cfc67b24df4eb3af845ff35c3dbf69e9fbfa9146a1a63950ca
Timestamp: 1716695826 Timestamp [UCT]: 2024-05-26 03:57:06 Age [y:d:h:m:s]: 00:360:06:10:38
Block: 1030169 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 257512 RingCT/type: yes/0
Extra: 01c3ee2d19dd1561cfc67b24df4eb3af845ff35c3dbf69e9fbfa9146a1a63950ca0211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 615710d9101ffa48df77506a7dfcb5c6a079338e6cf212d23240fab3e036e04b 0.600000000000 1498422 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": 1030179, "vin": [ { "gen": { "height": 1030169 } } ], "vout": [ { "amount": 600000000, "target": { "key": "615710d9101ffa48df77506a7dfcb5c6a079338e6cf212d23240fab3e036e04b" } } ], "extra": [ 1, 195, 238, 45, 25, 221, 21, 97, 207, 198, 123, 36, 223, 78, 179, 175, 132, 95, 243, 92, 61, 191, 105, 233, 251, 250, 145, 70, 161, 166, 57, 80, 202, 2, 17, 0, 0, 0, 2, 0, 17, 5, 91, 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