Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 14c44d62632da9d39e6c9cabfd3b89c5eba5b82a9f4d1d06dedf237d0c30f65c

Tx prefix hash: db5c4cbfc8b4c5fb52135e1a1ec761afe99022b7b93735ecf5b88a1d10e01e5b
Tx public key: 43f8d29964f3420ace27c96c94201680753f2cf15d3c1f94737efe52e8fa3c9f
Timestamp: 1725570932 Timestamp [UCT]: 2024-09-05 21:15:32 Age [y:d:h:m:s]: 00:225:14:00:08
Block: 1103745 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161069 RingCT/type: yes/0
Extra: 0143f8d29964f3420ace27c96c94201680753f2cf15d3c1f94737efe52e8fa3c9f021100000004e914dd15000000000000000000

1 output(s) for total of 0.608000000000 dcy

stealth address amount amount idx
00: 4475242cf103d488b006d1e8feb8e6813da4d5c19bd09619fa8cad566c45ba13 0.608000000000 1580690 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": 1103755, "vin": [ { "gen": { "height": 1103745 } } ], "vout": [ { "amount": 608000000, "target": { "key": "4475242cf103d488b006d1e8feb8e6813da4d5c19bd09619fa8cad566c45ba13" } } ], "extra": [ 1, 67, 248, 210, 153, 100, 243, 66, 10, 206, 39, 201, 108, 148, 32, 22, 128, 117, 63, 44, 241, 93, 60, 31, 148, 115, 126, 254, 82, 232, 250, 60, 159, 2, 17, 0, 0, 0, 4, 233, 20, 221, 21, 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