Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2fadc28dfc1790c5c23dbd11b538f55b1fc9d5971018ad1c32098925f9f400e6

Tx prefix hash: 1e7da1bd9ebd4a4efde978083d79ae2b7ed1d42410a45d23de816171f3e1bbc6
Tx public key: cddb517c2f70c710b878f415083f9cd8e16aeb8a0191b16184a778fa42f498ff
Timestamp: 1723914559 Timestamp [UCT]: 2024-08-17 17:09:19 Age [y:d:h:m:s]: 00:229:03:29:35
Block: 1090012 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 163636 RingCT/type: yes/0
Extra: 01cddb517c2f70c710b878f415083f9cd8e16aeb8a0191b16184a778fa42f498ff02110000000691e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 784a61598d9b911f35be3c54cf4b520448ef89df2f3d0007eef242cb2f34c149 0.600000000000 1564635 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": 1090022, "vin": [ { "gen": { "height": 1090012 } } ], "vout": [ { "amount": 600000000, "target": { "key": "784a61598d9b911f35be3c54cf4b520448ef89df2f3d0007eef242cb2f34c149" } } ], "extra": [ 1, 205, 219, 81, 124, 47, 112, 199, 16, 184, 120, 244, 21, 8, 63, 156, 216, 225, 106, 235, 138, 1, 145, 177, 97, 132, 167, 120, 250, 66, 244, 152, 255, 2, 17, 0, 0, 0, 6, 145, 225, 60, 4, 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