Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c04e8940542988580c550a59f59a083891d59229c6275f0abb053f5ba9861707

Tx prefix hash: 5f460aaa7c4076d938a5b174fe336df11b7d5f2df7fc7bf0ec758068ffcb17d1
Tx public key: e6234953d4dd17a844c68c7b78053b2a74e957cd3a6bd97017c500d50cae1de5
Timestamp: 1701497511 Timestamp [UCT]: 2023-12-02 06:11:51 Age [y:d:h:m:s]: 01:179:03:29:08
Block: 904153 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 389250 RingCT/type: yes/0
Extra: 01e6234953d4dd17a844c68c7b78053b2a74e957cd3a6bd97017c500d50cae1de502110000000346113aa8000000000000000000

1 output(s) for total of 0.619677541000 dcy

stealth address amount amount idx
00: b5a51e77683acd7404020e14d2d8f309f9daf93a9182fc9691fc6d23a3a27cb0 0.619677541000 1360862 of 0

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": 904163, "vin": [ { "gen": { "height": 904153 } } ], "vout": [ { "amount": 619677541, "target": { "key": "b5a51e77683acd7404020e14d2d8f309f9daf93a9182fc9691fc6d23a3a27cb0" } } ], "extra": [ 1, 230, 35, 73, 83, 212, 221, 23, 168, 68, 198, 140, 123, 120, 5, 59, 42, 116, 233, 87, 205, 58, 107, 217, 112, 23, 197, 0, 213, 12, 174, 29, 229, 2, 17, 0, 0, 0, 3, 70, 17, 58, 168, 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