Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8e95734fce20b3224eaaebeccb24ddd0d19a966bf99e88e83df5c1e83e0d8b5d

Tx prefix hash: 5afa64fdba92fb9edd6e6e8b81a4e730329eb21a9b4091c9d688b99cf4ef8d07
Tx public key: 62e4b852857654dade5f28d5c7bd601a728c4ce8b14f4da55ed743d85c06a0b0
Timestamp: 1705123009 Timestamp [UCT]: 2024-01-13 05:16:49 Age [y:d:h:m:s]: 01:010:18:41:52
Block: 934197 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 269000 RingCT/type: yes/0
Extra: 0162e4b852857654dade5f28d5c7bd601a728c4ce8b14f4da55ed743d85c06a0b002110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 32615e0b9eca2ab559d0012c58c9a61cb762834b113330f34842658651457b0b 0.600000000000 1392185 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": 934207, "vin": [ { "gen": { "height": 934197 } } ], "vout": [ { "amount": 600000000, "target": { "key": "32615e0b9eca2ab559d0012c58c9a61cb762834b113330f34842658651457b0b" } } ], "extra": [ 1, 98, 228, 184, 82, 133, 118, 84, 218, 222, 95, 40, 213, 199, 189, 96, 26, 114, 140, 76, 232, 177, 79, 77, 165, 94, 215, 67, 216, 92, 6, 160, 176, 2, 17, 0, 0, 0, 1, 89, 218, 211, 245, 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