Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 69a3ac2f084aee3501f01ecc2c1badb01815cc4e38a53ff7489f7bc4540a2d15

Tx prefix hash: 1ebca7250801d36ce1c7997d53f397096cc3ded4fb49a8580e2cd04c46ce85f7
Tx public key: 3e073c005a42343d3fe5bfa484b3f0654232b01d5feed4aa9264bdb7f0831d88
Timestamp: 1705386445 Timestamp [UCT]: 2024-01-16 06:27:25 Age [y:d:h:m:s]: 00:361:09:22:11
Block: 936365 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 258758 RingCT/type: yes/0
Extra: 013e073c005a42343d3fe5bfa484b3f0654232b01d5feed4aa9264bdb7f0831d8802110000000559dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4bc8ee40f26870f258c4b23abf5e0818f00303afe493b8429e81bd27c504b716 0.600000000000 1394389 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": 936375, "vin": [ { "gen": { "height": 936365 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4bc8ee40f26870f258c4b23abf5e0818f00303afe493b8429e81bd27c504b716" } } ], "extra": [ 1, 62, 7, 60, 0, 90, 66, 52, 61, 63, 229, 191, 164, 132, 179, 240, 101, 66, 50, 176, 29, 95, 238, 212, 170, 146, 100, 189, 183, 240, 131, 29, 136, 2, 17, 0, 0, 0, 5, 89, 218, 211, 245, 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