Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 20df41da5121088b2cc0484e2f3d7fb10b6e67c649918b33d650ccc6f54bd735

Tx prefix hash: ffbbc226d30278b316df5b111e7515307f88613217fbf39c7fe6a2049475b1d6
Tx public key: 1ca002892ffc1b89d6ae6ff6771eb60dfd22733ac8e05ad41c1e85270274cf76
Timestamp: 1677904170 Timestamp [UCT]: 2023-03-04 04:29:30 Age [y:d:h:m:s]: 02:100:23:08:44
Block: 709444 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 593740 RingCT/type: yes/0
Extra: 011ca002892ffc1b89d6ae6ff6771eb60dfd22733ac8e05ad41c1e85270274cf760211000000015029cbac000000000000000000

1 output(s) for total of 2.737268649000 dcy

stealth address amount amount idx
00: 5daa53639497cc50744e04e8cfb339db318e6a7fc026fd6e254d424ef1d3f0ea 2.737268649000 1153429 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": 709454, "vin": [ { "gen": { "height": 709444 } } ], "vout": [ { "amount": 2737268649, "target": { "key": "5daa53639497cc50744e04e8cfb339db318e6a7fc026fd6e254d424ef1d3f0ea" } } ], "extra": [ 1, 28, 160, 2, 137, 47, 252, 27, 137, 214, 174, 111, 246, 119, 30, 182, 13, 253, 34, 115, 58, 200, 224, 90, 212, 28, 30, 133, 39, 2, 116, 207, 118, 2, 17, 0, 0, 0, 1, 80, 41, 203, 172, 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