Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 67fce71b1714816d4ef6c71d71c7c5819e111740da92f1aaf1b101642f49e5bf

Tx prefix hash: 5c99ea6e61c15b888ef2d232f9a1ba8f2b1f2abc09e30671ef6a4b1abc2ce05d
Tx public key: 90971da4300f8a1740cfebb84c815d9d83abbca6095865803f488dde45db64d6
Timestamp: 1695609923 Timestamp [UCT]: 2023-09-25 02:45:23 Age [y:d:h:m:s]: 01:121:10:35:25
Block: 855548 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 348043 RingCT/type: yes/0
Extra: 0190971da4300f8a1740cfebb84c815d9d83abbca6095865803f488dde45db64d6021100000002e6d27f9c000000000000000000

1 output(s) for total of 0.897871879000 dcy

stealth address amount amount idx
00: 788eb018f3f7a90ac398fd0100a38e54bc3d4d9e92b0b8f6842a2f7b481ff700 0.897871879000 1309574 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": 855558, "vin": [ { "gen": { "height": 855548 } } ], "vout": [ { "amount": 897871879, "target": { "key": "788eb018f3f7a90ac398fd0100a38e54bc3d4d9e92b0b8f6842a2f7b481ff700" } } ], "extra": [ 1, 144, 151, 29, 164, 48, 15, 138, 23, 64, 207, 235, 184, 76, 129, 93, 157, 131, 171, 188, 166, 9, 88, 101, 128, 63, 72, 141, 222, 69, 219, 100, 214, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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