Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3b96ceb95c9948d4fc2154cc252bb57c1ceb29b3c513fc6baccbba6131beb743

Tx prefix hash: 2fbb7307d50ffc13c0a8cce86b77b89f27e90e64b1ec080fb8fb14b5b098f704
Tx public key: d88940412f9b011021da21e3a7074142bd0bbf846ab9dc57d307660ca3a59265
Timestamp: 1723628862 Timestamp [UCT]: 2024-08-14 09:47:42 Age [y:d:h:m:s]: 00:221:19:53:39
Block: 1087649 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 158399 RingCT/type: yes/0
Extra: 01d88940412f9b011021da21e3a7074142bd0bbf846ab9dc57d307660ca3a59265021100000010e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1b1f0a15bcc148cba76deb7d248294808b785a291926191103a30b7af5c717f9 0.600000000000 1562258 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": 1087659, "vin": [ { "gen": { "height": 1087649 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1b1f0a15bcc148cba76deb7d248294808b785a291926191103a30b7af5c717f9" } } ], "extra": [ 1, 216, 137, 64, 65, 47, 155, 1, 16, 33, 218, 33, 227, 167, 7, 65, 66, 189, 11, 191, 132, 106, 185, 220, 87, 211, 7, 102, 12, 163, 165, 146, 101, 2, 17, 0, 0, 0, 16, 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