Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 31ac2dff094ac15574bd0d89d6d261ac00a471e60cb3dcdc3e2b21a31ef571b3

Tx prefix hash: afaa6bc3b20e33f660717107c51bce2a0949a9641b078208e1d0da80a02862ef
Tx public key: 32827e8210c2ec23002c168b11135c45b8e4bbda57c07e8ac94a243b33d2d2bf
Timestamp: 1736167540 Timestamp [UCT]: 2025-01-06 12:45:40 Age [y:d:h:m:s]: 00:098:03:15:27
Block: 1191473 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69904 RingCT/type: yes/0
Extra: 0132827e8210c2ec23002c168b11135c45b8e4bbda57c07e8ac94a243b33d2d2bf021100000007007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9800932261aaf0e5701c95944c07d556714feecf695e0e63c8ca1a7a202d0f1e 0.600000000000 1678012 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": 1191483, "vin": [ { "gen": { "height": 1191473 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9800932261aaf0e5701c95944c07d556714feecf695e0e63c8ca1a7a202d0f1e" } } ], "extra": [ 1, 50, 130, 126, 130, 16, 194, 236, 35, 0, 44, 22, 139, 17, 19, 92, 69, 184, 228, 187, 218, 87, 192, 126, 138, 201, 74, 36, 59, 51, 210, 210, 191, 2, 17, 0, 0, 0, 7, 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