Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a0741a3568e782ad5eb5bb1feccdc5bf1741b0afac98579ab6210d48158124d

Tx prefix hash: 49b62b2ae52131ab2664835df5617d00e118447a19118c65f354d349b3c4c766
Tx public key: f10ca7e553ae02afc8d548d60b47e1484d4e339f3cf5c5e56c1951e4f2c40d9e
Timestamp: 1720905920 Timestamp [UCT]: 2024-07-13 21:25:20 Age [y:d:h:m:s]: 00:263:23:38:26
Block: 1065075 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 188583 RingCT/type: yes/0
Extra: 01f10ca7e553ae02afc8d548d60b47e1484d4e339f3cf5c5e56c1951e4f2c40d9e021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a37604fb424146dcdd1b8bc67baa98e180a85eab8fda45ad3d685986583d783c 0.600000000000 1535618 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": 1065085, "vin": [ { "gen": { "height": 1065075 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a37604fb424146dcdd1b8bc67baa98e180a85eab8fda45ad3d685986583d783c" } } ], "extra": [ 1, 241, 12, 167, 229, 83, 174, 2, 175, 200, 213, 72, 214, 11, 71, 225, 72, 77, 78, 51, 159, 60, 245, 197, 229, 108, 25, 81, 228, 242, 196, 13, 158, 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