Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 29a0daeeb29305072625964a1c5116aaacf192f3fd47ddef69de2f713a8d280b

Tx prefix hash: 59d02e35a9da131175d7d99b9c6b55473836d9a27f8b33a2fd0dbaf94e1abf41
Tx public key: d5b38ca6c099f101662ffca295b961c8e51f491c68d2891b718222222b5901c9
Timestamp: 1714707351 Timestamp [UCT]: 2024-05-03 03:35:51 Age [y:d:h:m:s]: 01:188:17:18:24
Block: 1013684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 393502 RingCT/type: yes/0
Extra: 01d5b38ca6c099f101662ffca295b961c8e51f491c68d2891b718222222b5901c90211000000020011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f598a14c2b17aa1b961e0a76106fe2b58addaeb0f219d7d667c09d6ab999220 0.600000000000 1476567 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": 1013694, "vin": [ { "gen": { "height": 1013684 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f598a14c2b17aa1b961e0a76106fe2b58addaeb0f219d7d667c09d6ab999220" } } ], "extra": [ 1, 213, 179, 140, 166, 192, 153, 241, 1, 102, 47, 252, 162, 149, 185, 97, 200, 229, 31, 73, 28, 104, 210, 137, 27, 113, 130, 34, 34, 43, 89, 1, 201, 2, 17, 0, 0, 0, 2, 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