Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 44a255a61e4d733b1e67ada04c18d40919413f951fbce4559a1ac6a4bad292c7

Tx prefix hash: 4278df6f3943c02eebbde4ca3ba20b509fcced50f0ff7ad4585193e40a151978
Tx public key: 6fb8bff966580bc63cad9970a27e95ae68c7c44e4e32fcc336f8bed1b50cab95
Timestamp: 1710721005 Timestamp [UCT]: 2024-03-18 00:16:45 Age [y:d:h:m:s]: 01:236:06:24:27
Block: 980646 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 427545 RingCT/type: yes/0
Extra: 016fb8bff966580bc63cad9970a27e95ae68c7c44e4e32fcc336f8bed1b50cab95021100000002679a8a81000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 44e81b6b03caf1e11f27c0fc72eee7201d3b0bdfcbd2495fd24999ee6cf008cf 0.600000000000 1440727 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": 980656, "vin": [ { "gen": { "height": 980646 } } ], "vout": [ { "amount": 600000000, "target": { "key": "44e81b6b03caf1e11f27c0fc72eee7201d3b0bdfcbd2495fd24999ee6cf008cf" } } ], "extra": [ 1, 111, 184, 191, 249, 102, 88, 11, 198, 60, 173, 153, 112, 162, 126, 149, 174, 104, 199, 196, 78, 78, 50, 252, 195, 54, 248, 190, 209, 181, 12, 171, 149, 2, 17, 0, 0, 0, 2, 103, 154, 138, 129, 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