Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 864b2c9735539a55cd1133e574326e3d0719de6f198411355c9f9d1799022453

Tx prefix hash: fd178daf89db103231cc98cb1c22210292322c295dafb80c76038ef6391a0a11
Tx public key: e5261cb24c6ad8510129204520da0f3b2c8d08cfae231fe56e8fee3a7fc863ae
Timestamp: 1701554094 Timestamp [UCT]: 2023-12-02 21:54:54 Age [y:d:h:m:s]: 01:082:18:27:20
Block: 904622 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 320271 RingCT/type: yes/0
Extra: 01e5261cb24c6ad8510129204520da0f3b2c8d08cfae231fe56e8fee3a7fc863ae02110000000a75e3f0e9000000000000000000

1 output(s) for total of 0.617464174000 dcy

stealth address amount amount idx
00: 444208cf49ed10509c4f6c4c1613d0c76ac1f172d4598170eff72deebc7b28aa 0.617464174000 1361389 of 0

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": 904632, "vin": [ { "gen": { "height": 904622 } } ], "vout": [ { "amount": 617464174, "target": { "key": "444208cf49ed10509c4f6c4c1613d0c76ac1f172d4598170eff72deebc7b28aa" } } ], "extra": [ 1, 229, 38, 28, 178, 76, 106, 216, 81, 1, 41, 32, 69, 32, 218, 15, 59, 44, 141, 8, 207, 174, 35, 31, 229, 110, 143, 238, 58, 127, 200, 99, 174, 2, 17, 0, 0, 0, 10, 117, 227, 240, 233, 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