Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52856e881b0f25c0609e8fa4e2a6961e38cd5bb20f6ad7883e16bb5a8ed4285b

Tx prefix hash: 548ddab19af7a8afdcec0c6ad77979c8b1d12fbd3023d8f91583133933a51162
Tx public key: cc964260eceefde3e8450c7107f2b8b72abdc291494a78a6d801fd6a842c8b50
Timestamp: 1711192857 Timestamp [UCT]: 2024-03-23 11:20:57 Age [y:d:h:m:s]: 01:229:00:33:15
Block: 984566 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 422352 RingCT/type: yes/0
Extra: 01cc964260eceefde3e8450c7107f2b8b72abdc291494a78a6d801fd6a842c8b500211000000037a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a999c62a51c5be819b97fe8ca1fb851f46dc81d98a5d6de364bea1aace2e5b65 0.600000000000 1444737 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": 984576, "vin": [ { "gen": { "height": 984566 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a999c62a51c5be819b97fe8ca1fb851f46dc81d98a5d6de364bea1aace2e5b65" } } ], "extra": [ 1, 204, 150, 66, 96, 236, 238, 253, 227, 232, 69, 12, 113, 7, 242, 184, 183, 42, 189, 194, 145, 73, 74, 120, 166, 216, 1, 253, 106, 132, 44, 139, 80, 2, 17, 0, 0, 0, 3, 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