Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bddbc186bc0c8712b5cef2007235524c5569d1e5340909e92ea1c625b1e834d1

Tx prefix hash: bde64a23a6ff7112e0463222231c45ea136e4b09090b6b8c884340bf37207bdc
Tx public key: 6aa34205c3634b85bb67a072cb53c18719d08bc7817fd5fddd4ef68635c3dc9f
Timestamp: 1737020294 Timestamp [UCT]: 2025-01-16 09:38:14 Age [y:d:h:m:s]: 00:340:14:18:30
Block: 1198513 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240981 RingCT/type: yes/0
Extra: 016aa34205c3634b85bb67a072cb53c18719d08bc7817fd5fddd4ef68635c3dc9f021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 04e051f087095136da882b089c51bd2ff18e3cf15aa9ff3523a3db9c251523d0 0.600000000000 1685138 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": 1198523, "vin": [ { "gen": { "height": 1198513 } } ], "vout": [ { "amount": 600000000, "target": { "key": "04e051f087095136da882b089c51bd2ff18e3cf15aa9ff3523a3db9c251523d0" } } ], "extra": [ 1, 106, 163, 66, 5, 195, 99, 75, 133, 187, 103, 160, 114, 203, 83, 193, 135, 25, 208, 139, 199, 129, 127, 213, 253, 221, 78, 246, 134, 53, 195, 220, 159, 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