Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e875607468133c3eb2822a7f6b9b5147a490710dd0c942a95c8cc237acbef525

Tx prefix hash: 456a38d2760864e79c7b163af070419b6d56ddd0dc773c852c75d0d605f35ebb
Tx public key: f8adcf7b9489f776a8160b055da80a2781ed912c3c9828a9f083e3accd7cf2b1
Timestamp: 1714958261 Timestamp [UCT]: 2024-05-06 01:17:41 Age [y:d:h:m:s]: 00:355:18:20:18
Block: 1015757 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 254324 RingCT/type: yes/0
Extra: 01f8adcf7b9489f776a8160b055da80a2781ed912c3c9828a9f083e3accd7cf2b10211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aaf5fd69436de2dc5614edf1c11b3ab7706cbf098b1bc8624c235e490dbc63b2 0.600000000000 1479198 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": 1015767, "vin": [ { "gen": { "height": 1015757 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aaf5fd69436de2dc5614edf1c11b3ab7706cbf098b1bc8624c235e490dbc63b2" } } ], "extra": [ 1, 248, 173, 207, 123, 148, 137, 247, 118, 168, 22, 11, 5, 93, 168, 10, 39, 129, 237, 145, 44, 60, 152, 40, 169, 240, 131, 227, 172, 205, 124, 242, 177, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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