Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 26cebb8042897710991faeb0d58630458c05b74c44e0325a0ff0f4ad6cf02805

Tx prefix hash: 72accd02e9c3bb19bfd8cc03a5595ee2a58a4677d0fd62fc63b5a9ca3fd580de
Tx public key: 929cf82c0a3f1754d5b9ac170fab911610b81bacdf80c68e7df360f6a24c6cea
Timestamp: 1730988449 Timestamp [UCT]: 2024-11-07 14:07:29 Age [y:d:h:m:s]: 00:136:01:14:49
Block: 1148566 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97074 RingCT/type: yes/0
Extra: 01929cf82c0a3f1754d5b9ac170fab911610b81bacdf80c68e7df360f6a24c6cea0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7250ba99a434ef88c3777a4cdf4a4d5fbe7ffa761fe65a03cde4c1a6fc7fbe37 0.600000000000 1633443 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": 1148576, "vin": [ { "gen": { "height": 1148566 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7250ba99a434ef88c3777a4cdf4a4d5fbe7ffa761fe65a03cde4c1a6fc7fbe37" } } ], "extra": [ 1, 146, 156, 248, 44, 10, 63, 23, 84, 213, 185, 172, 23, 15, 171, 145, 22, 16, 184, 27, 172, 223, 128, 198, 142, 125, 243, 96, 246, 162, 76, 108, 234, 2, 17, 0, 0, 0, 2, 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