Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b13638fac713b61791b2ad7d2e88529a6987e6d4c84896c678d9223b7a95357

Tx prefix hash: 7148402098453dae784e20edde1cf89534d96445ba92ac1199d7dc3eedd3e62d
Tx public key: c918b31e106274782fa09fde57d6a4e74aea5323ab0262b50a8d407397e9d329
Timestamp: 1735517298 Timestamp [UCT]: 2024-12-30 00:08:18 Age [y:d:h:m:s]: 00:098:04:36:31
Block: 1186065 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 69959 RingCT/type: yes/0
Extra: 01c918b31e106274782fa09fde57d6a4e74aea5323ab0262b50a8d407397e9d3290211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2eb88151f992f33a2eea148375b3a65c5343c06bf7a5f0df1e269994cd53c9a7 0.600000000000 1672540 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": 1186075, "vin": [ { "gen": { "height": 1186065 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2eb88151f992f33a2eea148375b3a65c5343c06bf7a5f0df1e269994cd53c9a7" } } ], "extra": [ 1, 201, 24, 179, 30, 16, 98, 116, 120, 47, 160, 159, 222, 87, 214, 164, 231, 74, 234, 83, 35, 171, 2, 98, 181, 10, 141, 64, 115, 151, 233, 211, 41, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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