Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d2246d186018db04606c12ca084bb2a6f95d74b9c9adf77c57ec60d8c87663dd

Tx prefix hash: 68ed9cb77eb59fd26443d3b3b206e39314e862c9b431cc578f20d1dbaf7ae281
Tx public key: 54d09779219afbf107df63b3b69ac979282c2356b044b775637845e8efe5f8b5
Timestamp: 1718523959 Timestamp [UCT]: 2024-06-16 07:45:59 Age [y:d:h:m:s]: 00:220:17:32:44
Block: 1045330 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 157907 RingCT/type: yes/0
Extra: 0154d09779219afbf107df63b3b69ac979282c2356b044b775637845e8efe5f8b502110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7ef4a6ef2ecb1b9d901e83088de34c6b9b64613eba470490071c6bfd6f06d619 0.600000000000 1514871 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": 1045340, "vin": [ { "gen": { "height": 1045330 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7ef4a6ef2ecb1b9d901e83088de34c6b9b64613eba470490071c6bfd6f06d619" } } ], "extra": [ 1, 84, 208, 151, 121, 33, 154, 251, 241, 7, 223, 99, 179, 182, 154, 201, 121, 40, 44, 35, 86, 176, 68, 183, 117, 99, 120, 69, 232, 239, 229, 248, 181, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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