Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71972df956f09a314a3d2354e52159536f8478e7715d07a4f1dec0c484d081e9

Tx prefix hash: 17acb41681e8d2969ee2f9a4301d03f017dd7995a5326e3169450c1d77acaa7c
Tx public key: 830c4397ab439941b2fb3fbba01493f14e64e4b9403cfb5ee227129726a585a3
Timestamp: 1732072819 Timestamp [UCT]: 2024-11-20 03:20:19 Age [y:d:h:m:s]: 00:004:07:22:28
Block: 1157545 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 3084 RingCT/type: yes/0
Extra: 01830c4397ab439941b2fb3fbba01493f14e64e4b9403cfb5ee227129726a585a3021100000002007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fcef47041b099c7bbf70588dd50a3ccb0e8a6574e74aed7820c02ff082c655b0 0.600000000000 1643168 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": 1157555, "vin": [ { "gen": { "height": 1157545 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fcef47041b099c7bbf70588dd50a3ccb0e8a6574e74aed7820c02ff082c655b0" } } ], "extra": [ 1, 131, 12, 67, 151, 171, 67, 153, 65, 178, 251, 63, 187, 160, 20, 147, 241, 78, 100, 228, 185, 64, 60, 251, 94, 226, 39, 18, 151, 38, 165, 133, 163, 2, 17, 0, 0, 0, 2, 0, 127, 151, 138, 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