Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be168c3d9db90ce7530810be5bca08be3e8b862458dcf1fe7bef2b9ea2b9c4b5

Tx prefix hash: 1f9a89eb333dc28e671e62d931ba63af7373d0724238f73fb32d66de6c0e4ce7
Tx public key: 634c3af57060ef3500290b6f2ad15009f360b0f0643c884d0978dcefdce0c0af
Timestamp: 1709631023 Timestamp [UCT]: 2024-03-05 09:30:23 Age [y:d:h:m:s]: 01:011:08:52:14
Block: 971605 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 269117 RingCT/type: yes/0
Extra: 01634c3af57060ef3500290b6f2ad15009f360b0f0643c884d0978dcefdce0c0af02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9ceed833a4f6ef63fde3bf058322e197aa63646ed8974e5e8550a444e16f0b80 0.600000000000 1431502 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": 971615, "vin": [ { "gen": { "height": 971605 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9ceed833a4f6ef63fde3bf058322e197aa63646ed8974e5e8550a444e16f0b80" } } ], "extra": [ 1, 99, 76, 58, 245, 112, 96, 239, 53, 0, 41, 11, 111, 42, 209, 80, 9, 243, 96, 176, 240, 100, 60, 136, 77, 9, 120, 220, 239, 220, 224, 192, 175, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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