Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 496f2b84d5def880ad8350f8b264aa87be1a289c01aeb3d329075166932c2c66

Tx prefix hash: 36802422a4e68afbfc29394c5dc1d826d174aac5abf4dd05e3fee45441d386cd
Tx public key: 448e55658059c05892a94e3ab5af50b0c5b2ed40f6299568989112bb11927dd4
Timestamp: 1580264104 Timestamp [UCT]: 2020-01-29 02:15:04 Age [y:d:h:m:s]: 04:333:18:17:17
Block: 54348 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1129470 RingCT/type: yes/0
Extra: 01448e55658059c05892a94e3ab5af50b0c5b2ed40f6299568989112bb11927dd4021100000001bd0f9f9f000000000000000000

1 output(s) for total of 405.436964522000 dcy

stealth address amount amount idx
00: b883454570fb0cb39eefe3d2fdc8e44dd435bad19e7d7620a11f0de913cc6c20 405.436964522000 100710 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": 54358, "vin": [ { "gen": { "height": 54348 } } ], "vout": [ { "amount": 405436964522, "target": { "key": "b883454570fb0cb39eefe3d2fdc8e44dd435bad19e7d7620a11f0de913cc6c20" } } ], "extra": [ 1, 68, 142, 85, 101, 128, 89, 192, 88, 146, 169, 78, 58, 181, 175, 80, 176, 197, 178, 237, 64, 246, 41, 149, 104, 152, 145, 18, 187, 17, 146, 125, 212, 2, 17, 0, 0, 0, 1, 189, 15, 159, 159, 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