Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6c37e9f0c3b64310c08e1a3d228014b265ec43465b7d86c25c01cf0c76b65251

Tx prefix hash: 80aeec079991d2be24ee8714aa389c29ebe4cfb2c9f47bc1a50d9f97067afb6d
Tx public key: b9a34d7dd1211cf18664a6b7070c52e7b5c09f83f571531fcf3715a63caffe2e
Timestamp: 1703722779 Timestamp [UCT]: 2023-12-28 00:19:39 Age [y:d:h:m:s]: 01:317:02:30:04
Block: 922612 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 485460 RingCT/type: yes/0
Extra: 01b9a34d7dd1211cf18664a6b7070c52e7b5c09f83f571531fcf3715a63caffe2e0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d502cd7cd8203e8e9ec2b18ffe00bd4bfbe56ad8ac756e1b98d05f81335dbb6f 0.600000000000 1380316 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": 922622, "vin": [ { "gen": { "height": 922612 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d502cd7cd8203e8e9ec2b18ffe00bd4bfbe56ad8ac756e1b98d05f81335dbb6f" } } ], "extra": [ 1, 185, 163, 77, 125, 209, 33, 28, 241, 134, 100, 166, 183, 7, 12, 82, 231, 181, 192, 159, 131, 245, 113, 83, 31, 207, 55, 21, 166, 60, 175, 254, 46, 2, 17, 0, 0, 0, 1, 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