Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c5b10a490d4598c76a3e629c44245923a993c0108bc2d2dad6ded4fbb9de767d

Tx prefix hash: cc26f098a696383bc6473f15c8333011225897bf74a8b2a4bc4130f398eb3c7e
Tx public key: e4cc9505a109852ae9199abd1185fda523e503793bf4846086a85ba97b5d4f7c
Timestamp: 1577611953 Timestamp [UCT]: 2019-12-29 09:32:33 Age [y:d:h:m:s]: 04:312:20:03:36
Block: 34273 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1112605 RingCT/type: yes/0
Extra: 01e4cc9505a109852ae9199abd1185fda523e503793bf4846086a85ba97b5d4f7c02110000000c4ac5aa02000000000000000000

1 output(s) for total of 472.541743805000 dcy

stealth address amount amount idx
00: 9c3d5d640a41aa78c7e228698fd0619dcf609961e04c69b5f68c5050448a4713 472.541743805000 57646 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": 34283, "vin": [ { "gen": { "height": 34273 } } ], "vout": [ { "amount": 472541743805, "target": { "key": "9c3d5d640a41aa78c7e228698fd0619dcf609961e04c69b5f68c5050448a4713" } } ], "extra": [ 1, 228, 204, 149, 5, 161, 9, 133, 42, 233, 25, 154, 189, 17, 133, 253, 165, 35, 229, 3, 121, 59, 244, 132, 96, 134, 168, 91, 169, 123, 93, 79, 124, 2, 17, 0, 0, 0, 12, 74, 197, 170, 2, 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