Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b115e7006d1e39c13b57ccee852c23cd56c7b102047b235d034e4b7392dff690

Tx prefix hash: 501614548c9dbe1b8895cd62336b4f322e3155e577169d94dcb4798ae6779051
Tx public key: 473dd6caea3815032d7d528264ba0420059d63ed82aa2dbdc15a2d7bd6d2ea48
Timestamp: 1713185411 Timestamp [UCT]: 2024-04-15 12:50:11 Age [y:d:h:m:s]: 01:058:00:48:24
Block: 1001055 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 302417 RingCT/type: yes/0
Extra: 01473dd6caea3815032d7d528264ba0420059d63ed82aa2dbdc15a2d7bd6d2ea480211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 838860727a5c5aa98c8d488cea796330b667d1332944bcb70b3ec2df1d05f313 0.600000000000 1461557 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": 1001065, "vin": [ { "gen": { "height": 1001055 } } ], "vout": [ { "amount": 600000000, "target": { "key": "838860727a5c5aa98c8d488cea796330b667d1332944bcb70b3ec2df1d05f313" } } ], "extra": [ 1, 71, 61, 214, 202, 234, 56, 21, 3, 45, 125, 82, 130, 100, 186, 4, 32, 5, 157, 99, 237, 130, 170, 45, 189, 193, 90, 45, 123, 214, 210, 234, 72, 2, 17, 0, 0, 0, 5, 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