Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 91afec8f4907c949b891c21f370c255ae1598b214b8417834c77450fd2e37e84

Tx prefix hash: 24c63b7567bb5143a5375bcd72f41f2a9c3bc469056f58d3c68b959a085b9283
Tx public key: 4c99fab0c9987f3e57eb896476f73d3277630a24a81798ae32c601621d3bd61e
Timestamp: 1736128378 Timestamp [UCT]: 2025-01-06 01:52:58 Age [y:d:h:m:s]: 00:094:20:56:55
Block: 1191139 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67580 RingCT/type: yes/0
Extra: 014c99fab0c9987f3e57eb896476f73d3277630a24a81798ae32c601621d3bd61e0211000000101f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 94f4d4667cbe3160ad2a9b4df08ecdf98218292f03ceb1f67da368ea247822f7 0.600000000000 1677662 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": 1191149, "vin": [ { "gen": { "height": 1191139 } } ], "vout": [ { "amount": 600000000, "target": { "key": "94f4d4667cbe3160ad2a9b4df08ecdf98218292f03ceb1f67da368ea247822f7" } } ], "extra": [ 1, 76, 153, 250, 176, 201, 152, 127, 62, 87, 235, 137, 100, 118, 247, 61, 50, 119, 99, 10, 36, 168, 23, 152, 174, 50, 198, 1, 98, 29, 59, 214, 30, 2, 17, 0, 0, 0, 16, 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