Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5d365750a8582d5e8fb5df30cc45c879d026121b9a3290455158b2ebe79f61b3

Tx prefix hash: 2788797314633b6f37935abc4d9611d2450047875b20da51cac5e98f6af4286b
Tx public key: 74f4df1a206dc9854dae9d2579ac956625f03fd509c2f507b45ef92f69c99bf8
Timestamp: 1737777277 Timestamp [UCT]: 2025-01-25 03:54:37 Age [y:d:h:m:s]: 00:143:12:36:32
Block: 1204738 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102327 RingCT/type: yes/0
Extra: 0174f4df1a206dc9854dae9d2579ac956625f03fd509c2f507b45ef92f69c99bf80211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 47d361e4340bcbee3d34ff7f6f5f47f15f8f7bd718c31ff0e3a8baa2c5320dfe 0.600000000000 1691431 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": 1204748, "vin": [ { "gen": { "height": 1204738 } } ], "vout": [ { "amount": 600000000, "target": { "key": "47d361e4340bcbee3d34ff7f6f5f47f15f8f7bd718c31ff0e3a8baa2c5320dfe" } } ], "extra": [ 1, 116, 244, 223, 26, 32, 109, 201, 133, 77, 174, 157, 37, 121, 172, 149, 102, 37, 240, 63, 213, 9, 194, 245, 7, 180, 94, 249, 47, 105, 201, 155, 248, 2, 17, 0, 0, 0, 7, 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