Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1eb585f4d435bb9360e93bd01712d6583cb2e3e8713e7ea5aef238b2a4c90e91

Tx prefix hash: 3e70a52da5038fd5f1639305feacd7d42e780e4fb85cbe9f157e71a7831b2e26
Tx public key: 378356cf0470ffab896c455d41b720b218e6d7066e5f426efc266e2789c5758c
Timestamp: 1750071893 Timestamp [UCT]: 2025-06-16 11:04:53 Age [y:d:h:m:s]: 00:157:21:43:08
Block: 1306192 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110636 RingCT/type: yes/0
Extra: 01378356cf0470ffab896c455d41b720b218e6d7066e5f426efc266e2789c5758c021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 222b02b16a82dc02bf4cc481f8bfe872fc0039afb23e9352aa8ebece9742ac1e 0.600000000000 1793795 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": 1306202, "vin": [ { "gen": { "height": 1306192 } } ], "vout": [ { "amount": 600000000, "target": { "key": "222b02b16a82dc02bf4cc481f8bfe872fc0039afb23e9352aa8ebece9742ac1e" } } ], "extra": [ 1, 55, 131, 86, 207, 4, 112, 255, 171, 137, 108, 69, 93, 65, 183, 32, 178, 24, 230, 215, 6, 110, 95, 66, 110, 252, 38, 110, 39, 137, 197, 117, 140, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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