Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c32aa8ca93894f55ef0d15fdc7b823391a6d4b32253077bbfa66e1ecf7a28f11

Tx prefix hash: 9e702ce1de2120a4d0f664245a1dd49827fdb58ff1077e1dd070dcc6cac3c693
Tx public key: e5175789d499b9d50b6569d1efa3dc2098af3eed51f12a611321a6e309a4b545
Timestamp: 1741242267 Timestamp [UCT]: 2025-03-06 06:24:27 Age [y:d:h:m:s]: 00:215:18:26:56
Block: 1233201 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151891 RingCT/type: yes/0
Extra: 01e5175789d499b9d50b6569d1efa3dc2098af3eed51f12a611321a6e309a4b545021100000008007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b6b6150570290e8ef86326ae84b3b77a3c2a7aa8b40a24097ee2c238816d5c2 0.600000000000 1720120 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": 1233211, "vin": [ { "gen": { "height": 1233201 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b6b6150570290e8ef86326ae84b3b77a3c2a7aa8b40a24097ee2c238816d5c2" } } ], "extra": [ 1, 229, 23, 87, 137, 212, 153, 185, 213, 11, 101, 105, 209, 239, 163, 220, 32, 152, 175, 62, 237, 81, 241, 42, 97, 19, 33, 166, 227, 9, 164, 181, 69, 2, 17, 0, 0, 0, 8, 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