Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea607c7a45a1ee5204ce4104f88017208fd4bd47a3e592aa26c9bbf0c51a38e5

Tx prefix hash: 3830488a84b65ff9dda7e4b8834e4346be6abe582baf1910c649a38c55e5bb16
Tx public key: 75866be6cfc6b56cb9d8341f93685a14228cc75ef7b238f4f6c3d21caaa5bf09
Timestamp: 1705049714 Timestamp [UCT]: 2024-01-12 08:55:14 Age [y:d:h:m:s]: 01:025:16:09:10
Block: 933593 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 279419 RingCT/type: yes/0
Extra: 0175866be6cfc6b56cb9d8341f93685a14228cc75ef7b238f4f6c3d21caaa5bf090211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ebc9fe91cb11467a6711b7ec57b9141357e1c76302aae481d7581db1d7193978 0.600000000000 1391561 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": 933603, "vin": [ { "gen": { "height": 933593 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ebc9fe91cb11467a6711b7ec57b9141357e1c76302aae481d7581db1d7193978" } } ], "extra": [ 1, 117, 134, 107, 230, 207, 198, 181, 108, 185, 216, 52, 31, 147, 104, 90, 20, 34, 140, 199, 94, 247, 178, 56, 244, 246, 195, 210, 28, 170, 165, 191, 9, 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