Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f722846ee854d11191a52bcf8c04598937786c6f9e2cb8c153470a50754e09c6

Tx prefix hash: b3c43deb38d94045977f2c1a757927e2014388401c94074153f42850d71f8807
Tx public key: 669f81782b2adb990366775123ab1dc3f773847b0c8e1b7d2f38f1be59772ab1
Timestamp: 1701513147 Timestamp [UCT]: 2023-12-02 10:32:27 Age [y:d:h:m:s]: 01:338:03:05:46
Block: 904284 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 500537 RingCT/type: yes/0
Extra: 01669f81782b2adb990366775123ab1dc3f773847b0c8e1b7d2f38f1be59772ab102110000000375e3f0e9000000000000000000

1 output(s) for total of 0.626858511000 dcy

stealth address amount amount idx
00: a96bed6cdfd8f30583ce9a45c8e600d2c298716bd89f6079cb4a09bd7051dfbf 0.626858511000 1361011 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": 904294, "vin": [ { "gen": { "height": 904284 } } ], "vout": [ { "amount": 626858511, "target": { "key": "a96bed6cdfd8f30583ce9a45c8e600d2c298716bd89f6079cb4a09bd7051dfbf" } } ], "extra": [ 1, 102, 159, 129, 120, 43, 42, 219, 153, 3, 102, 119, 81, 35, 171, 29, 195, 247, 115, 132, 123, 12, 142, 27, 125, 47, 56, 241, 190, 89, 119, 42, 177, 2, 17, 0, 0, 0, 3, 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