Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ab110ecb08dbfa937f101a3aaf08317a6d9977f970d656bdd2565c4fb7fc4b05

Tx prefix hash: 0b1abc2d495712624ea81f4d0b092020dc4b12300a406ecfa9c92fec14b57048
Tx public key: c2d50db068e6c04e57fe3f2358e55bff991a1ea17bbfa53f50bac18cd898abf5
Timestamp: 1706779195 Timestamp [UCT]: 2024-02-01 09:19:55 Age [y:d:h:m:s]: 01:047:12:50:42
Block: 947927 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 295068 RingCT/type: yes/0
Extra: 01c2d50db068e6c04e57fe3f2358e55bff991a1ea17bbfa53f50bac18cd898abf50211000000040011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2d28686dbaf0fa6ce13d3c9556afc148999789bc945c4b9f4a6eaa4aa91c0c94 0.600000000000 1406287 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": 947937, "vin": [ { "gen": { "height": 947927 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2d28686dbaf0fa6ce13d3c9556afc148999789bc945c4b9f4a6eaa4aa91c0c94" } } ], "extra": [ 1, 194, 213, 13, 176, 104, 230, 192, 78, 87, 254, 63, 35, 88, 229, 91, 255, 153, 26, 30, 161, 123, 191, 165, 63, 80, 186, 193, 140, 216, 152, 171, 245, 2, 17, 0, 0, 0, 4, 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