Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 12d4a65ff4f5e34dc68c9a0363ff45eb9a8043d9139488ee0160501555922fa1

Tx prefix hash: 85d7006375adedce3f97998f216a5adc97895eab0b4ea90cf9e87a6ac045b06d
Tx public key: 61d7b6e659bf64c207e498b2e50681e1d6b586b9b9f082dfc9582e284646375a
Timestamp: 1706169754 Timestamp [UCT]: 2024-01-25 08:02:34 Age [y:d:h:m:s]: 01:075:09:17:43
Block: 942865 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 314978 RingCT/type: yes/0
Extra: 0161d7b6e659bf64c207e498b2e50681e1d6b586b9b9f082dfc9582e284646375a02110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b11c6b2537a156ccef9a8b83f8232ab864e82db05c2bcda7d05f7111130dbcee 0.600000000000 1401045 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": 942875, "vin": [ { "gen": { "height": 942865 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b11c6b2537a156ccef9a8b83f8232ab864e82db05c2bcda7d05f7111130dbcee" } } ], "extra": [ 1, 97, 215, 182, 230, 89, 191, 100, 194, 7, 228, 152, 178, 229, 6, 129, 225, 214, 181, 134, 185, 185, 240, 130, 223, 201, 88, 46, 40, 70, 70, 55, 90, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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