Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1fca20ea2f383f9e8cd371d990c2353501bddcfff0c9a4913e0217e944b5b880

Tx prefix hash: cb5e5ec728c7effb0efd8cf9492a87e13e71d0fbc3dd3c07b9b6c5e704df2a8f
Tx public key: 64769be077df7c553a961d03952db2b792a438dc4af5aec8a67d233b0cc95a39
Timestamp: 1657724798 Timestamp [UCT]: 2022-07-13 15:06:38 Age [y:d:h:m:s]: 02:248:17:48:30
Block: 542959 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 698909 RingCT/type: yes/0
Extra: 0164769be077df7c553a961d03952db2b792a438dc4af5aec8a67d233b0cc95a39021100000002e6d27f9c000000000000000000

1 output(s) for total of 9.748809468000 dcy

stealth address amount amount idx
00: 4301f18f6976cf45521330ab0b82fe3fdd7c89b25e66beeb3cb737cd97994899 9.748809468000 973574 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": 542969, "vin": [ { "gen": { "height": 542959 } } ], "vout": [ { "amount": 9748809468, "target": { "key": "4301f18f6976cf45521330ab0b82fe3fdd7c89b25e66beeb3cb737cd97994899" } } ], "extra": [ 1, 100, 118, 155, 224, 119, 223, 124, 85, 58, 150, 29, 3, 149, 45, 178, 183, 146, 164, 56, 220, 74, 245, 174, 200, 166, 125, 35, 59, 12, 201, 90, 57, 2, 17, 0, 0, 0, 2, 230, 210, 127, 156, 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