Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c4bf2dc3127131209ec64d2cb2a6200b3bc53b8637b686720e8d0fa162dacda3

Tx prefix hash: ccd627f31b8757cf8022f451f3484aa9e62a5352b1ff727f0451addc2f6eca89
Tx public key: 914f2f1397eb39e1578202ae2ea6c8e555091f391e3a2f822cb1f427a09662b4
Timestamp: 1737017330 Timestamp [UCT]: 2025-01-16 08:48:50 Age [y:d:h:m:s]: 00:152:09:30:45
Block: 1198487 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108626 RingCT/type: yes/0
Extra: 01914f2f1397eb39e1578202ae2ea6c8e555091f391e3a2f822cb1f427a09662b4021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 09ecfce6b6a079ffdd08f1f81f3a8afa0180a5afcde2fe92170f25c17181dea0 0.600000000000 1685112 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": 1198497, "vin": [ { "gen": { "height": 1198487 } } ], "vout": [ { "amount": 600000000, "target": { "key": "09ecfce6b6a079ffdd08f1f81f3a8afa0180a5afcde2fe92170f25c17181dea0" } } ], "extra": [ 1, 145, 79, 47, 19, 151, 235, 57, 225, 87, 130, 2, 174, 46, 166, 200, 229, 85, 9, 31, 57, 30, 58, 47, 130, 44, 177, 244, 39, 160, 150, 98, 180, 2, 17, 0, 0, 0, 4, 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