Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bcdcea6c01fc2b11d0b5a04c4b1dde74da9c1aba8b213f49c5c3fcbcdbb6c475

Tx prefix hash: 050cc88a9d6ff522fc5b575524ad5e384909c5b594b1930f03b1368df7b06038
Tx public key: dd48505411853a8f3c485a184e85bd3ece0f853e218155960983333b86c79110
Timestamp: 1720825697 Timestamp [UCT]: 2024-07-12 23:08:17 Age [y:d:h:m:s]: 00:245:15:44:37
Block: 1064415 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 175500 RingCT/type: yes/0
Extra: 01dd48505411853a8f3c485a184e85bd3ece0f853e218155960983333b86c7911002110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f33c3b0b7d2d4a3712e4a02fe1ab5d7084933d4b834c6c12d3cb09c6d17965a2 0.600000000000 1534940 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": 1064425, "vin": [ { "gen": { "height": 1064415 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f33c3b0b7d2d4a3712e4a02fe1ab5d7084933d4b834c6c12d3cb09c6d17965a2" } } ], "extra": [ 1, 221, 72, 80, 84, 17, 133, 58, 143, 60, 72, 90, 24, 78, 133, 189, 62, 206, 15, 133, 62, 33, 129, 85, 150, 9, 131, 51, 59, 134, 199, 145, 16, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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