Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a5416c91eab431a1cce1dd98f4147aaf55e04a30634cae8c9b24350d346fbe5b

Tx prefix hash: fc32a833c11a45f03725f35e9731efa7f6f4639b48a4532da5395d247b2dd1e3
Tx public key: 7d65b27f0ea4f5357b9156176d163d8d9027558a6dac23fb0ba4ee5776682ed8
Timestamp: 1723919914 Timestamp [UCT]: 2024-08-17 18:38:34 Age [y:d:h:m:s]: 00:242:10:09:21
Block: 1090062 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 173135 RingCT/type: yes/0
Extra: 017d65b27f0ea4f5357b9156176d163d8d9027558a6dac23fb0ba4ee5776682ed8021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9e8120141f308239ec002fb539102a20f30f6c8c39e1dfce9b30581535b45627 0.600000000000 1564685 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": 1090072, "vin": [ { "gen": { "height": 1090062 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9e8120141f308239ec002fb539102a20f30f6c8c39e1dfce9b30581535b45627" } } ], "extra": [ 1, 125, 101, 178, 127, 14, 164, 245, 53, 123, 145, 86, 23, 109, 22, 61, 141, 144, 39, 85, 138, 109, 172, 35, 251, 11, 164, 238, 87, 118, 104, 46, 216, 2, 17, 0, 0, 0, 2, 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