Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7c921b751d2c66200c10f12047fd806bf84545f8821ae31a67c1b070c4d95b7

Tx prefix hash: cfce1fab72b702702227fc2cb8bcfe7e2ad9cb71aacf7d50f2e344f66ae5653d
Tx public key: febdd47f47f15a0097c2e8bdb75d7a2cecb663d18cb27c65190a4f158d9075d4
Timestamp: 1737130568 Timestamp [UCT]: 2025-01-17 16:16:08 Age [y:d:h:m:s]: 00:339:07:18:09
Block: 1199420 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240060 RingCT/type: yes/0
Extra: 01febdd47f47f15a0097c2e8bdb75d7a2cecb663d18cb27c65190a4f158d9075d40211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f1a8573f91222a8b4561dde4cb12b7e4cb20463efcb8f54eef3d82090283fd8c 0.600000000000 1686051 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": 1199430, "vin": [ { "gen": { "height": 1199420 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f1a8573f91222a8b4561dde4cb12b7e4cb20463efcb8f54eef3d82090283fd8c" } } ], "extra": [ 1, 254, 189, 212, 127, 71, 241, 90, 0, 151, 194, 232, 189, 183, 93, 122, 44, 236, 182, 99, 209, 140, 178, 124, 101, 25, 10, 79, 21, 141, 144, 117, 212, 2, 17, 0, 0, 0, 4, 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