Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c84cbc60d2f71a61173ceda4078ccbd173a9ee2eaa450d0c65b0dfea53959137

Tx prefix hash: fc60d8795bb3013a7aec2a2629940741d2274b30e3bab8b926f9d50f99d765a3
Tx public key: 55fc2bb2f140629b963c4c3fbded9863e1ddba130fa83f41c2f3f01e65bce53c
Timestamp: 1674341916 Timestamp [UCT]: 2023-01-21 22:58:36 Age [y:d:h:m:s]: 02:035:06:36:48
Block: 679901 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 546821 RingCT/type: yes/0
Extra: 0155fc2bb2f140629b963c4c3fbded9863e1ddba130fa83f41c2f3f01e65bce53c021100000001faf35c9c000000000000000000

1 output(s) for total of 3.429301658000 dcy

stealth address amount amount idx
00: 45332e56b284f5c222647857ee0f4d4ce1ca71d171563444547cafded99289a3 3.429301658000 1121914 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": 679911, "vin": [ { "gen": { "height": 679901 } } ], "vout": [ { "amount": 3429301658, "target": { "key": "45332e56b284f5c222647857ee0f4d4ce1ca71d171563444547cafded99289a3" } } ], "extra": [ 1, 85, 252, 43, 178, 241, 64, 98, 155, 150, 60, 76, 63, 189, 237, 152, 99, 225, 221, 186, 19, 15, 168, 63, 65, 194, 243, 240, 30, 101, 188, 229, 60, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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