Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 492c43e59e2f64794f3ee4a9251040b60753a1366069e19da2f7579deb6c60e2

Tx prefix hash: 01be4a6e100279747c887590880c376d841a29f4ae53a79c0fbdd46cf59c0f06
Tx public key: ed552c1685eea6b10fe0c25b17394649db86d36db0bf7f88ca6f7f6ffc9de8a5
Timestamp: 1708541030 Timestamp [UCT]: 2024-02-21 18:43:50 Age [y:d:h:m:s]: 01:093:00:23:15
Block: 962551 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327538 RingCT/type: yes/0
Extra: 01ed552c1685eea6b10fe0c25b17394649db86d36db0bf7f88ca6f7f6ffc9de8a50211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5c61d3771ddc08ab0c7ed1ea5166afc82f401712e39c370e92d5b6ff29688d51 0.600000000000 1422192 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": 962561, "vin": [ { "gen": { "height": 962551 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5c61d3771ddc08ab0c7ed1ea5166afc82f401712e39c370e92d5b6ff29688d51" } } ], "extra": [ 1, 237, 85, 44, 22, 133, 238, 166, 177, 15, 224, 194, 91, 23, 57, 70, 73, 219, 134, 211, 109, 176, 191, 127, 136, 202, 111, 127, 111, 252, 157, 232, 165, 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