Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 19c67cc225d0c912e71ee9f3f10c6a4ac2b035f38f93b9e8b5c6b656dd6ef5bf

Tx prefix hash: de7d4df126aea32d6e3555e25ad0d731fee5c55753384666eace7fef6eb03f75
Tx public key: 644163e13952831b9cc512e00bfb2576caf8b8fdb340229c790d841103eca10d
Timestamp: 1685377542 Timestamp [UCT]: 2023-05-29 16:25:42 Age [y:d:h:m:s]: 01:334:01:26:59
Block: 770774 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 499964 RingCT/type: yes/0
Extra: 01644163e13952831b9cc512e00bfb2576caf8b8fdb340229c790d841103eca10d02110000000575e3f0e9000000000000000000

1 output(s) for total of 1.714375483000 dcy

stealth address amount amount idx
00: 8aa9a361d0ed35adc63aa0fc6da5755320a5aae9515ce90201f74e59bbe0e75b 1.714375483000 1220103 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": 770784, "vin": [ { "gen": { "height": 770774 } } ], "vout": [ { "amount": 1714375483, "target": { "key": "8aa9a361d0ed35adc63aa0fc6da5755320a5aae9515ce90201f74e59bbe0e75b" } } ], "extra": [ 1, 100, 65, 99, 225, 57, 82, 131, 27, 156, 197, 18, 224, 11, 251, 37, 118, 202, 248, 184, 253, 179, 64, 34, 156, 121, 13, 132, 17, 3, 236, 161, 13, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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