Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc476865545826ec5f817fe90c07bf2384eb90987bc6db72b5777d82419b2cf7

Tx prefix hash: 4682cfc1c5ed0be5663ca14969dd8fb2a7b7eece2d73a0ac1d3c85d74e984e89
Tx public key: ae1ac593babb065c8f9aa529b7b83428f844e7c6785c5e2871dcb66862e11106
Timestamp: 1723766948 Timestamp [UCT]: 2024-08-16 00:09:08 Age [y:d:h:m:s]: 00:100:15:54:15
Block: 1088789 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 72007 RingCT/type: yes/0
Extra: 01ae1ac593babb065c8f9aa529b7b83428f844e7c6785c5e2871dcb66862e11106021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b0d71e1aaad625524d80ffa887168507e184f24e31e82e3815edbf6bbf9f47fa 0.600000000000 1563408 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": 1088799, "vin": [ { "gen": { "height": 1088789 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b0d71e1aaad625524d80ffa887168507e184f24e31e82e3815edbf6bbf9f47fa" } } ], "extra": [ 1, 174, 26, 197, 147, 186, 187, 6, 92, 143, 154, 165, 41, 183, 184, 52, 40, 248, 68, 231, 198, 120, 92, 94, 40, 113, 220, 182, 104, 98, 225, 17, 6, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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