Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b2f62ed1c08593c97e87120740684f7c9f7e7dfe3399da3f258c985eaa370c43

Tx prefix hash: e19cd7d3e3a2138147fe7d2df08da42766b4c08f0e6e139b980d120ff1f15fcf
Tx public key: a0933944ecf010e9c50116fb02d14c207f70d23bb24b1ca9f6826f20a9c97776
Timestamp: 1631621486 Timestamp [UCT]: 2021-09-14 12:11:26 Age [y:d:h:m:s]: 04:047:14:15:28
Block: 333601 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1068027 RingCT/type: yes/0
Extra: 01a0933944ecf010e9c50116fb02d14c207f70d23bb24b1ca9f6826f20a9c9777602110000002e8d0de867000000000000000000

1 output(s) for total of 48.155050640000 dcy

stealth address amount amount idx
00: e1305f83c4ecb8097a33a72beca8368c448592ff5d901e420ea795d12053fe73 48.155050640000 688334 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": 333611, "vin": [ { "gen": { "height": 333601 } } ], "vout": [ { "amount": 48155050640, "target": { "key": "e1305f83c4ecb8097a33a72beca8368c448592ff5d901e420ea795d12053fe73" } } ], "extra": [ 1, 160, 147, 57, 68, 236, 240, 16, 233, 197, 1, 22, 251, 2, 209, 76, 32, 127, 112, 210, 59, 178, 75, 28, 169, 246, 130, 111, 32, 169, 201, 119, 118, 2, 17, 0, 0, 0, 46, 141, 13, 232, 103, 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