Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b0cd82c57cbee1f5dceb483cb978c7411a5601182559efc44fb36b813dae949a

Tx prefix hash: 8dc7e4c1ea89406976c15f3559c32647ead11320b0bc20f5f2ed88cc8eeaf248
Tx public key: 444fa622f2ad045b3775a59b8def3635f9c74538fd8ac6805cdd4cfb99a1a042
Timestamp: 1738257537 Timestamp [UCT]: 2025-01-30 17:18:57 Age [y:d:h:m:s]: 00:041:09:44:40
Block: 1208495 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 29628 RingCT/type: yes/0
Extra: 01444fa622f2ad045b3775a59b8def3635f9c74538fd8ac6805cdd4cfb99a1a0420211000000091f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: fbbee1cb0a660e79210b0f10e3fde9d1ed2b26fbb3f2022cfcdb998fac50ab4b 0.600000000000 1695228 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": 1208505, "vin": [ { "gen": { "height": 1208495 } } ], "vout": [ { "amount": 600000000, "target": { "key": "fbbee1cb0a660e79210b0f10e3fde9d1ed2b26fbb3f2022cfcdb998fac50ab4b" } } ], "extra": [ 1, 68, 79, 166, 34, 242, 173, 4, 91, 55, 117, 165, 155, 141, 239, 54, 53, 249, 199, 69, 56, 253, 138, 198, 128, 92, 221, 76, 251, 153, 161, 160, 66, 2, 17, 0, 0, 0, 9, 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