Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1265332eca0d6133909fc4cdaebca1c25bd8f9452d688d5e14c36a92c3ce1df3

Tx prefix hash: 547fe94a80c279e1c92e6b56fb691e8e596bdd524829712dc990378551d3bbea
Tx public key: cd08a5e9adc4b9f7b46661a4318ac516e44092fb161218e1b11a455213ff4445
Timestamp: 1708148624 Timestamp [UCT]: 2024-02-17 05:43:44 Age [y:d:h:m:s]: 01:045:02:40:23
Block: 959293 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 293270 RingCT/type: yes/0
Extra: 01cd08a5e9adc4b9f7b46661a4318ac516e44092fb161218e1b11a455213ff44450211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c62ca6a93ee2a210fdf3411013672925ffc04dc4d7cdbd8f0330614e42b740b8 0.600000000000 1418828 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": 959303, "vin": [ { "gen": { "height": 959293 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c62ca6a93ee2a210fdf3411013672925ffc04dc4d7cdbd8f0330614e42b740b8" } } ], "extra": [ 1, 205, 8, 165, 233, 173, 196, 185, 247, 180, 102, 97, 164, 49, 138, 197, 22, 228, 64, 146, 251, 22, 18, 24, 225, 177, 26, 69, 82, 19, 255, 68, 69, 2, 17, 0, 0, 0, 5, 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