Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0cf5f0ac34578e583771797c347c4e474cbaf2f5c4c8cfd47dceeef520a4749c

Tx prefix hash: c11f1ccd858bb2a1bd825c8fbf8def873b7417245318ec8f2edb51e560cb9868
Tx public key: fe5fe9a5e3a61af7cb6a79e55aa7ab1baffa7ca8a69cb76ec5d1b1b1d6d05611
Timestamp: 1725460256 Timestamp [UCT]: 2024-09-04 14:30:56 Age [y:d:h:m:s]: 00:252:08:15:51
Block: 1102831 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180220 RingCT/type: yes/0
Extra: 01fe5fe9a5e3a61af7cb6a79e55aa7ab1baffa7ca8a69cb76ec5d1b1b1d6d0561102110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 536efd813a18638ca7f1d7c0f3e83b18079d40b00ef38870dcda9022f9edbcf4 0.600000000000 1579418 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": 1102841, "vin": [ { "gen": { "height": 1102831 } } ], "vout": [ { "amount": 600000000, "target": { "key": "536efd813a18638ca7f1d7c0f3e83b18079d40b00ef38870dcda9022f9edbcf4" } } ], "extra": [ 1, 254, 95, 233, 165, 227, 166, 26, 247, 203, 106, 121, 229, 90, 167, 171, 27, 175, 250, 124, 168, 166, 156, 183, 110, 197, 209, 177, 177, 214, 208, 86, 17, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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