Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8cfe899252bc648b360875361eb386691ecb79daa2fd0b7cc6f64181a9ec86b2

Tx prefix hash: db3993ad97804f7e6f676b1b2cf547685ee12d0e8c6afb6a7bf1eded50560be6
Tx public key: 27867782366b4102bbdc8ba1b5a2faf61bdc997864b9b5c4afc37cc47a5d2cc6
Timestamp: 1703587507 Timestamp [UCT]: 2023-12-26 10:45:07 Age [y:d:h:m:s]: 01:096:23:56:58
Block: 921485 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330433 RingCT/type: yes/0
Extra: 0127867782366b4102bbdc8ba1b5a2faf61bdc997864b9b5c4afc37cc47a5d2cc60211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: be255c5bbe9e59af9f5bb20ad5710c0d94bbc4ef2d392719dd92ed8a32f2fec6 0.600000000000 1379173 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": 921495, "vin": [ { "gen": { "height": 921485 } } ], "vout": [ { "amount": 600000000, "target": { "key": "be255c5bbe9e59af9f5bb20ad5710c0d94bbc4ef2d392719dd92ed8a32f2fec6" } } ], "extra": [ 1, 39, 134, 119, 130, 54, 107, 65, 2, 187, 220, 139, 161, 181, 162, 250, 246, 27, 220, 153, 120, 100, 185, 181, 196, 175, 195, 124, 196, 122, 93, 44, 198, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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